Does this mean that people upgrading to latest MO2 will lose their color settings? If yes, is there a way to migrate?

They seem to be stored in the Windows registry under HKEY_CURRENT_USER\Software\QtProject\OrganizationDefaults\Qt\customColors. Should we add an option in the installer to migrate them to ModOrganizer.ini?

Might be better to use MO2's upgrade functions to look for and import those settings if they are not defined in the local config.

@JonathanFeenstra I would like to merge this but I think we should try importing the previous color settings. There should be an upgrade function when we detect a new MO2 version. I don't think it has to be handled by the installer.

I also don't think we should delete those registry entries since each MO2 instance would have to save the color settings now.

There's MainWindow::processUpdates that calls this:

I'm assuming the next release version number will be 2.6.0. I tested that the copyGlobalCustomColors I added works correctly by overwriting currentVersion to 2.6.0 using the debugger on this line:

I suppose we'll use 2.6. Testers can always drop their version number back to 2.5.2 in the mo.ini to test the upgrade process. Each instance tracks that separately.

I think this looks fine. I'll include it in the beta but I suppose we'll need to test in the 2.6.0 RC.

Should have noticed sooner and it would probably only be an issue for people running the betas, but we may want to only transfer the color settings if values haven't already been set (or are the default values).